home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000138_misckit-reques…aska.et.byu.edu_Thu Feb 17 10:34:16 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
3KB
Return-Path: <misckit-request@alaska.et.byu.edu>
Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA00828; Thu, 17 Feb 94 10:33:22 -0700
Received: from darth.byu.edu by alaska.et.byu.edu; Thu, 17 Feb 1994 10:32:47 -0700
Received: by darth.byu.edu (NX5.67d/NX3.0M)
id AA00821; Thu, 17 Feb 94 10:31:28 -0700
Date: Thu, 17 Feb 94 10:31:28 -0700
From: Don Yacktman <don@darth.byu.edu>
Message-Id: <9402171731.AA00821@darth.byu.edu>
Received: by NeXT.Mailer (1.100)
Received: by NeXT Mailer (1.100)
To: misckit@alaska.et.byu.edu
Subject: Re: Breaking MiscKit into separate "levels"
Reply-To: don@darth.byu.edu
> Why is it necessary to have Object as a level?
Well, here's my line of reasoning, but I don't know enough
about Obj-C on non-NeXT platforms, so I could be a bit off the
mark here.
The idea was that List and HashTable are "NeXT" objects,
and when you link an ObjC program, they are available to
you under NEXTSTEP. But what about other platforms?
Are these classes always available, like object, when you
link ObjC? If so, then that level 1 and 2 should be the same.
If not, then it seems they should be different; level 1 should
be OK to use in any ObjC, but level 2 would require the user
to add in HashTable and List. Now, I know that there are free
NeXT-compatible HashTable and List classes out there, but
I thought you had to add them in by hand. Wehn I saw them,
they were a separate product, and not with the Object class.
If that has changed...
So that's what I was thinking. Level 1/2 were both still supposed
to work on other ObjC platforms, though so it's no big deal if they
were the same. In that case, in fact, I'd say that the fewer
divisions we have the metter, since that makes things easier
to work with for the user, by far. (In other words, I saw an artificial
division out there, in the non-NeXT world...but that doesn't mean
it is necessarily still there or worth paying attention to, really.)
I guess maybe that suggestion wasn't so bright...because even if
List and HashTable aren't automatically included (are they?) you
could make them a requirement for MiscKit users. In fact, perhaps
even have the MiscKit include them in level 1 automatically on
non-NeXT platforms...
After Michael's description of the palette library, I can easily see
where that would be a good thing. Too bad it isn't working just
yet. The idea is really nice. With all the palettes in the MiscKit,
such a beast would be a really useful aid to MiscKit programmers.
(However, it seems almost to be more of a sideways step from the
other libraries rather than a direct descendant...) Well, it is
something else to think about adding to the kit someday... :-)
calling the libraries libMisc.a, libMiscKit.a, and libMiscAppKit.a
sounds like a good approach, and is as good as anythings else
I might come up with. And Michael's header structure sounds
like a good way to go.
Oh, and on Object...
> >A common object protocol is necessary. (Mr Pugh?)
> This must be resolved, but not my a lowly mortal like myself.
There wouldn't have been a problem if NeXT went with what
Brad Cox already had. what were their reasons for deviation?
Were there really good reasons, or was it just for ego?
---
Later,
-Don Yacktman
Don_Yacktman@byu.edu